feat(bounty): manage-dashboard nav + deep-linkable tabs (#637)#676
Conversation
|
@Benjtalkshow is attempting to deploy a commit to the Threadflow Team on Vercel. A member of the Team first needs to authorize it. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
fa9edb1 to
75fc65f
Compare
) Wire the org bounty list into the operate dashboard: published cards get a status-aware CTA (review / pay / results) that deep-links to the right tab, and the dashboard honors a ?tab= param (validated against what's available for the bounty). Wrap the dashboard in a suspense boundary now that it reads useSearchParams.
75fc65f to
cbaeac1
Compare
What
Implements the nav wiring for #637 (Bounty Operate to Payout — entry points + e2e verification): connects the org bounty list to the operate dashboard and makes the dashboard tabs deep-linkable.
Changes
BountyManagementDashboard.tsx— tabs are URL-addressable via?tab=, validated against what's actually available for the bounty (applicationsonly in application modes,resultsonly once completed; otherwise falls back to Overview).organizations/[id]/bounties/page.tsx— each published card gets an explicit, status-aware CTA that deep-links to the relevant tab: Review submissions (submitted / under review), Review & pay (in progress), View results (completed), View bounty (cancelled), Manage otherwise.[bountyId]/page.tsx— wrapped the dashboard in a<Suspense>boundary (required now that it readsuseSearchParams), matching the existingverify/page.tsxprecedent.Task status
npm run codegen— already current; the generated schema carries every merged epic endpoint (submissions review, operate reads, publish-results, archive/restore, public results/announcement). Disputes are intentionally absent (Feat/hackthon features #340/FE: Dispute resolution UI #636 deferred).Verification
tsc --noEmit— 0 errors.eslint .— clean.